home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d21
/
386pcbdv.arc
/
386PCBDV.TXT
next >
Wrap
Text File
|
1988-02-29
|
14KB
|
287 lines
386PCBDV.TXT
By Joseph Sheppard
The Ledge PCBoard (818) 352-3620
This file describes the method I have used to run three nodes (two
live and one with no modem for the Sysop) using PCBoard 12.0, Desqview
2.00 and Quarterdeck's Expanded Memory Manager 386 on a 16 MHz AMI 386
AT.
I am writing this file because at this time, very few systems are
running multi-nodes under Desqview on an 80386 based machine using the
virtual 86 mode. It took quite a bit of help from two local Sysops,
Tom Tcimpidis of The MOG-UR'S EMS (818) 366-1238 and Ken Ough of
LUNACY PCBoard (818) 894-1248. Without the help I received from Tom
and Ken, I'm not sure I would have been able to figure it out.
It is assumed that the reader is running a machine with an 80386
microprocessor running at least 16 MHz, and that you are very familiar
with PCBoard 12.0, Desqview 2.00 and QEMM 4.0.
My specific system includes 3072 K of RAM. All the memory above 640K
is eXtended memory. QEMM 4.0 will convert standard eXtended memory on
a 386 machine into exPanded memory that can be used for running
programs. If you are running more or less memory, you can adjust the
figures mentioned here to match your system. You will probably need
at least 2 megabytes of extended RAM in order to run 2 live PCBoard
nodes and have enough room left for a good sized third window.
One of the problems I encountered is that the Desqview manual assumes
that there is a single user on the system that is present at the
terminal while multi-tasking is taking place. Many of the default
settings assume that the user wants the most speed and processing
power put toward the program in the foreground. A multi-node BBS,
however, can have two remote users with a third at the local
keyboard. Nobody wants to be on the short end of the stick!
Using the settings described here I have been able to run both nodes
of the BBS and a third window for my use as either a no-modem node, or
just space to play around in at very respectable speeds. I happen to
run a USRobotics Courier HST modem on node 1 with the port open at
19200 baud. My log constantly reflects cps ratings ranging from
1000-1500 cps for the high speed callers, while another caller is
present on node 2, and I am busy in a third window.
CONFIG.SYS
-----------
The first thing to alter is your CONFIG.SYS. Mine looks like this:
DEVICE=QEMM.SYS MEMORY=1732
DEVICE=EDISK.SYS 700 256 200 /E
FCBS=32,32
FILES=32
BUFFERS=50
As stated above, I have 3072 K of RAM. Take away 640K conventional
memory and that leaves 2432 K to play with.
DEVICE=QEMM.SYS MEMORY=1732
---------------------------
Converts 1732 K into exPanded memory that can be used to run programs
in the virtual 86 mode.
DEVICE=EDISK.SYS 700 256 200 /E
-------------------------------
A RAM disk is a great way to cut down disk access. I place all my read
only files in RAM. These include most of my \PCB\GEN directory and the
entire \PCB\HELP directory. You may rather use the memory for running
programs. If that's the case, just let QEMM convert all your eXtended
memory. I use a Ramdisk program called EDISK that came with my extended
memory card. This command creates a 700K RAM disk in eXtended memory
that can handle 200 entries. Other RAM disk drivers that are able to
create eXtended memory RAM disks can be used.
FCBS=32,32
----------
This is the setting required to run PCBoard with a multi-tasker as
discussed in PCBOARD.DOC.
FILES=32
--------
This is the Files statement required to run PCBoard with a
multi-tasker as discussed in PCBOARD.DOC.
BUFFERS=50
----------
I was running my buffers way lower than this, but disk access under
three windows got really sluggish. Again, play with it, but you will
probably end up setting them fairly high.
DESQVIEW SETUP
--------------
Go into your Desqview directory and type SETUP. Go to the performance
menu. Mine looks like this:
╔1══Advanced═Setup:═Performance══════════╗
║ ║
║ Task Processing Time (in Clock Ticks) ║
║ Foreground: 1 ║
║ Background: 1 ║
║ ║
║ Memory Usage (in K) ║
║ Common Memory: 12 ║
║ DOS Buffer for EMS: 30 ║
║ ║
║ Optimize communications? (Y/N): Y ║
║ Allow swapping of programs? (Y/N): Y ║
║ Manage printer contention? (Y/N): Y ║
║ ║
║ Next field Tab ║
║ Backup menu Esc ║
║ DONE ─┘ ║
║ ║
╚════════════════════════════════════════╝
TASK PROCESSING TIME (in Clock Ticks)
-------------------------------------
The default settings here were Foreground: 9, Background: 3. From
remote the system looked like PCBoard re-written for the Commodore
Vic-20! Really slow and jerky with callers on both nodes. For awhile
I ran it with 3 and 3, then 2 and 2, but these settings, while
providing VERY smooth scrolling at all modem speeds still caused
erratic remote keyboard entry. Kind of like PC Pursuit, where you type
and the text on the screen is about 3 letters behind you. The
Desqview manual says not to set it below 2 and 2, but with my system 1
and 1 provided smooth scrolling and excellent remote keyboard entry.
Memory Usage (in K)
--------------------
Common Memory: 12 is the default. Didn't seem to improve anything
when I changed it to higher, so I just kept it there.
DOS Buffer for EMS: 30. The default is 2K. The maximum that the manual
states is effective is 30. Because I was looking for performance rather
than efficient use of memory, I chose the maximum. If your available
memory dwindles too low, this would be place you could cut back without
a big loss of performance.
Optimize Communications?
------------------------
This is the default. No change.
Allow swapping of programs?
---------------------------
Yes is the default. Nothing exploded, so I didn't change it.
However, as the manual states, DO NOT allow a modem program to be
swapped out of memory!
Manage Printer Contention?
--------------------------
The default is NO. This one had to be changed to fix what seemed to be
a totally unrelated problem. While running Desqview, I couldn't seem to
use the CTTY command to go to DOS from remote. From the local side, I
could type CTTY COM1 from the DOS prompt, and instead of disappearing
to COM1, it would just bounce the DOS prompt back at me again like
nothing had happened. Finally I called Quarterdeck and they told me to
change this setting to YES. This fixed the problem, while (at this
point anyway) not causing any new ones.
PROGRAM INFORMATION
-------------------
All three of my PCBoard nodes are set-up exactly the same as far as
memory allocated, and general options. The first set-up screen for
node 1 looks like this:
╔1══Change═a═Program═══════════════════════════════════════════════════════════╗
║ Change a Program ║
║ ║
║ Program Name............: PCBoard Node 1 ║
║ ║
║ Keys to Use on Open Menu: N1 Memory Size (in K): 300 ║
║──────────────────────────────────────────────────────────────────────────────║
║ Program...: d:\pcb\dvpcb ║
║ ║
║ Parameters: ║
║ ║
║ Directory.: d:\pcb ║
║──────────────────────────────────────────────────────────────────────────────║
║ Options: ║
║ Writes directly to screen......: [N] ║
║ Displays graphics information..: [N] ║
║ Can be swapped out of memory...: [N] ║
║ Requires floppy diskette.......: [N] ║
║ ║
║ Press F1 for advanced options Press ─┘ when you are DONE ║
╚══════════════════════════════════════════════════════════════════════════════╝
Memory Size in K:
-----------------
Can be less, but I made it 300K just to be sure. All functions seem to
work fine with this allocation. Jump To DOS, Doors and External
Protocols all function fine. Even under this high overhead for
performance set-up you should still be able to allocate over 400K to a
window if need be.
Program....d:\pcb\dvpcb
-----------------------
DVPCB is a batch file I use to first load DVANSI.COM (The Desqview
ANSI driver) then execute BOARD.BAT
Can be swapped out of memory
----------------------------
As with ANY communications program under Desqview, this should always
be set to NO.
ADVANCED OPTIONS
----------------
Hit F1 to go to the Advanced Options menu..some things will require
changing. Here is my Advanced option screen for Node 1:
╔1══Change═a═Program═══════════════════════════════════════════════════════════╗
║ Change a Program Advanced Options ║
║ ║
║ System Memory (in K).......: 0 Maximum Program Memory Size (in K)..: ║
║ ║
║ Script Buffer Size.......: 1000 Maximum Expanded Memory Size (in K): ║
║ ║
║ Text Pages: 1 Graphics Pages: 0 Initial Mode: Interrupts: 00 to FF ║
║──────────────────────────────────────────────────────────────────────────────║
║ Window Position: ║
║ Maximum Height: 25 Starting Height: 25 Starting Row...: 0 ║
║ Maximum Width.: 80 Starting Width.: 80 Starting Column: 0 ║
║──────────────────────────────────────────────────────────────────────────────║
║ Shared Program ║
║ Pathname..: ║
║ ║
║ Data......: ║
║──────────────────────────────────────────────────────────────────────────────║
║ Options: ║
║ Close on exit to DOS.........: [N] Uses its own colors.........: [Y] ║
║ Allow Close Window command...: [Y] Runs only in foreground.....: [N] ║
║ Uses math coprocessor........: [N] Keyboard conflict (0-4).....: [0] ║
║ ║
║ Press F1 for standard options Press ─┘ when you are DONE ║
╚══════════════════════════════════════════════════════════════════════════════╝
Starting Height: 25
Starting Width.: 80
-------------------
This will keep Desqview from sticking you in a half sized window. To
switch between nodes just tap ALT twice real fast.
Uses it's own colors : Y
------------------------
Set this to YES if you want PCBoards normal colors instead of
Desqview's reverse screen stuff.
Runs only in foreground: N
--------------------------
Set this to NO to insure that Desqview won't stop one of your nodes
because it's in background.
These are the specific things that I had to change to get it to run on
my system. Yours may be different. I am reachable on my BBS which is
listed at the top of page one if you need assistance. I am also
available on CIS at 73175,623, PLINK at J.SHEPPARD or GEnie at
J.SHEPPARD.
Good Luck!
-Joseph Sheppard